XXXXSSSSGGGGIIIIvvvvccccSSSSeeeettttSSSSccccrrrreeeeeeeennnnIIIInnnnppppuuuuttttSSSSyyyynnnnccccSSSSoooouuuurrrrcccceeee sets the server's Screen sync
source to the internal or external source.
XXXXSSSSGGGGIIIIvvvvccccQQQQuuuueeeerrrryyyySSSSccccrrrreeeeeeeennnnIIIInnnnppppuuuuttttSSSSyyyynnnnccccSSSSoooouuuurrrrcccceeee returns the current
settings of the sync source for the server's Screen. This
function also returns the current state of the lock.
For servers with more than one external sync source,
XXXXSSSSGGGGIIIIvvvvccccSSSSeeeettttSSSSccccrrrreeeeeeeennnnEEEExxxxtttteeeerrrrnnnnaaaallllSSSSyyyynnnnccccSSSSoooouuuurrrrcccceeee selects which external
source is to be used for locking. The structure returned by
the function XXXXSSSSGGGGIIIIvvvvccccQQQQuuuueeeerrrryyyyVVVViiiiddddeeeeooooSSSSccccrrrreeeeeeeennnnIIIInnnnffffoooo has a member field
containing the number of external sync sources. The
function XXXXSSSSGGGGIIIIvvvvccccQQQQuuuueeeerrrryyyySSSSccccrrrreeeeeeeennnnEEEExxxxtttteeeerrrrnnnnaaaallllSSSSyyyynnnnccccSSSSoooouuuurrrrcccceeee returns the
currently selected external sync source. Selecting an
external sync source with XXXXSSSSGGGGIIIIvvvvccccSSSSeeeettttSSSSccccrrrreeeeeeeennnnEEEExxxxtttteeeerrrrnnnnaaaallllSSSSyyyynnnnccccSSSSoooouuuurrrrcccceeee
does not switch from the internal to the external sync
source; it is still necessary to use the function
XXXXSSSSGGGGIIIIvvvvccccSSSSeeeettttSSSSccccrrrreeeeeeeennnnIIIInnnnppppuuuuttttSSSSyyyynnnnccccSSSSoooouuuurrrrcccceeee to switch from internal to
external sync source.
For convenience in presenting information to a user,
XXXXSSSSGGGGIIIIvvvvccccQQQQuuuueeeerrrryyyyEEEExxxxtttteeeerrrrnnnnaaaallllSSSSyyyynnnnccccSSSSoooouuuurrrrcccceeeeNNNNaaaammmmeeee returns the textual name
associated with the sync source. You must free the returned
string with XFree.
EEEEVVVVEEEENNNNTTTTSSSS
The sync source state change event reports dynamic input
sync source state changes. The server generates a
SSSSccccrrrreeeeeeeennnnLLLLoooocccckkkkSSSSttttaaaattttuuuussssCCCChhhhaaaannnnggggeeeeddddNNNNoooottttiiiiffffyyyy event when the server
achieves or loses lock. This allows you to determine when a
server achieves lock. The server may not be able to report
intervening instances of rapidly changing lock state and
therefore may report two consecutive instances of the same
state; client programs must check the value of the status
variable reported in the event to determine the state of the
lock.
When this control is altered, the server generates a
XXXXSSSSGGGGIIIIvvvvccccQQQQuuuueeeerrrryyyySSSSccccrrrreeeeeeeennnnIIIInnnnppppuuuuttttSSSSyyyynnnnccccSSSSoooouuuurrrrcccceeee returns TRUE if successful,
FALSE upon failure.
Parameter errors are reported via BadValue or BadMatch.